⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

Command failed: uv lock --upgrade-package pyjwt
Using CPython 3.14.3 interpreter at: /opt/containerbase/tools/python/3.14.3/bin/python3
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version == '3.8.*'):
  ╰─▶ Because only pyjwt{python_full_version < '3.9'}<=2.11.0 is available
      and the requested Python version (>=3.8) does not satisfy Python>=3.9,
      we can conclude that pyjwt{python_full_version < '3.9'}>=2.11.0 cannot
      be used.
      And because your project depends on pyjwt{python_full_version <
      '3.9'}>=2.11, we can conclude that your project's requirements are
      unsatisfiable.

      hint: While the active Python version is 3.14, the resolution failed for
      other Python versions supported by your project. Consider limiting your
      project's supported Python versions using `requires-python`.

Greptile Overview

Greptile Summary

This PR updates the pyjwt dependency constraint for Python 3.8 from >=2.9.0,<2.10 to >=2.11,<2.12. However, this creates an inconsistency: Python 3.9+ environments allow pyjwt>=2.10.0 (no upper bound), while Python 3.8 now requires version 2.11+. This inverts the original pattern where Python 3.8 used older versions.

The update appears to be an automated Renovate PR, but the logic needs adjustment. The Python 3.9+ constraint should likely be updated to match, or the Python 3.8 constraint should maintain an upper bound at <2.12 while keeping the lower bound at >=2.10.0 for consistency.

Major issues:

• Version constraint mismatch between Python versions creates unpredictable behavior across environments
• Python 3.8 will now use newer pyjwt versions (2.11.x) than Python 3.9+ installations that happen to have 2.10.x installed

Confidence Score: 2/5

• This PR introduces inconsistent dependency constraints that could cause version mismatches across Python environments
• The dependency update creates a logical inconsistency where Python 3.8 will use newer pyjwt versions (2.11+) than Python 3.9+ environments (which allow 2.10+). This breaks the expected pattern and could lead to different behavior across Python versions. The constraints should be aligned.
• pyproject.toml requires attention to align pyjwt version constraints across Python versions

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Renovate as Renovate Bot
    participant Deps as pyproject.toml
    participant Py38 as Python 3.8 Environment
    participant Py39 as Python 3.9+ Environment
    participant PyJWT as PyJWT Library
    
    Renovate->>Deps: Update pyjwt constraint for Python 3.8
    Note over Deps: Before: pyjwt>=2.9.0,<2.10 (Python 3.8)
    Note over Deps: After: pyjwt>=2.11,<2.12 (Python 3.8)
    Note over Deps: Unchanged: pyjwt>=2.10.0 (Python 3.9+)
    
    Py38->>Deps: Install dependencies
    Deps->>PyJWT: Request pyjwt>=2.11,<2.12
    PyJWT-->>Py38: Install 2.11.x
    
    Py39->>Deps: Install dependencies
    Deps->>PyJWT: Request pyjwt>=2.10.0
    PyJWT-->>Py39: Install 2.10.x or 2.11.x (no upper bound)
    
    Note over Py38,Py39: Inconsistency: Python 3.8 mandates 2.11+<br/>while Python 3.9+ allows 2.10+